Modeling the Application of IHE QRPH Profiles in Data Integration Centers: A Practical Approach with 3LGM2.

The Data Integration Centers (DICs), all part of the German Medical Informatics Initiative (MII), prepare routine care data captured in university hospitals to enable its reuse in clinical research. Tackling this challenging task requires them to maintain multiple data stores, implement the necessary transformation processes, and provide the required terminology services, all while also addressing the use case specific needs researchers might have. An MII wide application of the standardized profiles defined in the IHE QRPH domain might therefore be able to drastically reduce the overhead at any one DIC. The MII DIC reference model built in 3LGM2, a method to describe complex information system architectures, serves as a starting point to evaluate whether such an application is possible. We first extend the IHE modeling capabilities of 3LGM2 to also support the five profiles from the QRPH domain that our experts evaluated as relevant in the MII DIC context. We then expand the DIC reference model by some IHE QRPH actors and transactions, showing that their application could be beneficial in the MII DIC context, provided they surpass their trial status.

A FHIR has been lit on gICS: facilitating the standardised exchange of informed consent in a large network of university medicine.

BACKGROUND: The Federal Ministry of Education and Research of Germany (BMBF) funds a network of university medicines (NUM) to support COVID-19 and pandemic research at national level. The "COVID-19 Data Exchange Platform" (CODEX) as part of NUM establishes a harmonised infrastructure that supports research use of COVID-19 datasets. The broad consent (BC) of the Medical Informatics Initiative (MII) is agreed by all German federal states and forms the legal base for data processing. All 34 participating university hospitals (NUM sites) work upon a harmonised infrastructural as well as legal basis for their data protection-compliant collection and transfer of their research dataset to the central CODEX platform. Each NUM site ensures that the exchanged consent information conforms to the already-balloted HL7 FHIR consent profiles and the interoperability concept of the MII Task Force "Consent Implementation" (TFCI). The Independent Trusted Third-Party (TTP) of the University Medicine Greifswald supports data protection-compliant data processing and provides the consent management solutions gICS. METHODS: Based on a stakeholder dialogue a required set of FHIR-functionalities was identified and technically specified supported by official FHIR experts. Next, a "TTP-FHIR Gateway" for the HL7 FHIR-compliant exchange of consent information using gICS was implemented. A last step included external integration tests and the development of a pre-configured consent template for the BC for the NUM sites. RESULTS: A FHIR-compliant gICS-release and a corresponding consent template for the BC were provided to all NUM sites in June 2021. All FHIR functionalities comply with the already-balloted FHIR consent profiles of the HL7 Working Group Consent Management. The consent template simplifies the technical BC rollout and the corresponding implementation of the TFCI interoperability concept at the NUM sites. CONCLUSIONS: This article shows that a HL7 FHIR-compliant and interoperable nationwide exchange of consent information could be built using of the consent management software gICS and the provided TTP-FHIR Gateway. The initial functional scope of the solution covers the requirements identified in the NUM-CODEX setting. The semantic correctness of these functionalities was validated by project-partners from the Ludwig-Maximilian University in Munich. The production rollout of the solution package to all NUM sites has started successfully.

3LGM2IHE: Requirements for Data-Protection-Compliant Research Infrastructures-A Systematic Comparison of Theory and Practice-Oriented Implementation.

OBJECTIVES: The TMF (Technology, Methods, and Infrastructure for Networked Medical Research) Data Protection Guide (TMF-DP) makes path-breaking recommendations on the subject of data protection in research projects. It includes comprehensive requirements for applications such as patient lists, pseudonymization services, and consent management services. Nevertheless, it lacks a structured, categorized list of requirements for simplified application in research projects and systematic evaluation. The 3LGM2IHE ("Three-layer Graphbased meta model - Integrating the Healthcare Enterprise [IHE] " ) project is funded by the German Research Foundation (DFG). 3LGM2IHE aims to define modeling paradigms and implement modeling tools for planning health care information systems. In addition, one of the goals is to create and publish 3LGM2 information system architecture design patterns (short "design patterns") for the community as design models in terms of a framework. A structured list of data protection-related requirements based on the TMF-DP is a precondition to integrate functions (3LGM2 Domain Layer) and building blocks (3LGM2 Logical Tool Layer) in 3LGM2 design patterns. METHODS: In order to structure the continuous text of the TMF-DP, requirement types were defined in a first step. In a second step, dependencies and delineations of the definitions were identified. In a third step, the requirements from the TMF-DP were systematically extracted. Based on the identified lists of requirements, a fourth step included the comparison of the identified requirements with exemplary open source tools as provided by the "Independent Trusted Third Party of the University Medicine Greifswald" (TTP tools). RESULTS: As a result, four lists of requirements were created, which contain requirements for the "patient list", the "pseudonymization service", and the "consent management", as well as cross-component requirements from the TMF-DP chapter 6 in a structured form. Further to requirements (1), possible variants (2) of implementations (to fulfill a single requirement) and recommendations (3) were identified. A comparison of the requirements lists with the functional scopes of the open source tools E-PIX (record linkage), gPAS (pseudonym management), and gICS (consent management) has shown that these fulfill more than 80% of the requirements. CONCLUSIONS: A structured set of data protection-related requirements facilitates a systematic evaluation of implementations with respect to the fulfillment of the TMF-DP guidelines. These re-usable lists provide a decision aid for the selection of suitable tools for new research projects. As a result, these lists form the basis for the development of data protection-related 3LGM2 design patterns as part of the 3LGM2IHE project.

The Leipzig Health Atlas-An Open Platform to Present, Archive, and Share Biomedical Data, Analyses, and Models Online.

BACKGROUND: Clinical trials, epidemiological studies, clinical registries, and other prospective research projects, together with patient care services, are main sources of data in the medical research domain. They serve often as a basis for secondary research in evidence-based medicine, prediction models for disease, and its progression. This data are often neither sufficiently described nor accessible. Related models are often not accessible as a functional program tool for interested users from the health care and biomedical domains. OBJECTIVE: The interdisciplinary project Leipzig Health Atlas (LHA) was developed to close this gap. LHA is an online platform that serves as a sustainable archive providing medical data, metadata, models, and novel phenotypes from clinical trials, epidemiological studies, and other medical research projects. METHODS: Data, models, and phenotypes are described by semantically rich metadata. The platform prefers to share data and models presented in original publications but is also open for nonpublished data. LHA provides and associates unique permanent identifiers for each dataset and model. Hence, the platform can be used to share prepared, quality-assured datasets and models while they are referenced in publications. All managed data, models, and phenotypes in LHA follow the FAIR principles, with public availability or restricted access for specific user groups. RESULTS: The LHA platform is in productive mode (https://www.health-atlas.de/). It is already used by a variety of clinical trial and research groups and is becoming increasingly popular also in the biomedical community. LHA is an integral part of the forthcoming initiative building a national research data infrastructure for health in Germany.

A Formal Model for the FAIR4Health Information Architecture.

In the EU project FAIR4Health, a ETL pipeline for the FAIRification of structured health data as well as an agent-based, distributed query platform for the analysis of research hypotheses and the training of machine learning models were developed. The system has been successfully tested in two clinical use cases with patient data from five university hospitals. Currently, the solution is also being considered for use in other hospitals. However, configuring the system and deploying it in the local IT architecture is non-trivial and meets with understandable concerns about security. This paper presents a model for describing the information architecture based on a formal approach, the 3LGM metamodel. The model was evaluated by the developers. As a result, the clear separation of tasks and the software components that implement them as well as the rich description of interactions via interfaces were positively emphasized.

ToolPool Gesundheitsforschung - A Repository for Software and Services Focused on Supporting Clinical and Epidemiological Research.

The academic research environment is characterized by self-developed, innovative, customized solutions, which are often free to use for third parties with open-source code and open licenses. On the other hand, they are maintained only to a very limited extent after the end of project funding. The ToolPool Gesundheitsforschung addresses the problem of finding ready to use solutions by building a registry of proven and supported tools, services, concepts and consulting offers. The goal is to provide an up-to-date selection of "relevant" solutions for a given domain that are immediately usable and that are actually used by third parties, rather than aiming at a complete list of all solutions which belong to that domain. Proof of relevance and usage must be provided, for example, by concrete application scenarios, experience reports by uninvolved third parties, references in publications or workshops held. Quality assurance is carried out for new entries by an agreed list of admission criteria, for existing entries at least once a year by a special task force. Currently, 79 solutions are represented, this number is to be significantly expanded by involving of new editors from current national funding initiatives in Germany.

Ontological Modelling and Execution of Phenotypic Queries in the Leipzig Health Atlas.

Sharing data is of great importance for research in medical sciences. It is the basis for reproducibility and reuse of already generated outcomes in new projects and in new contexts. FAIR data principles are the basics for sharing data. The Leipzig Health Atlas (LHA) platform follows these principles and provides data, describing metadata, and models that have been implemented in novel software tools and are available as demonstrators. LHA reuses and extends three different major components that have been previously developed by other projects. The SEEK management platform is the foundation providing a repository for archiving, presenting and secure sharing a wide range of publication results, such as published reports, (bio)medical data as well as interactive models and tools. The LHA Data Portal manages study metadata and data allowing to search for data of interest. Finally, PhenoMan is an ontological framework for phenotype modelling. This paper describes the interrelation of these three components. In particular, we use the PhenoMan to, firstly, model and represent phenotypes within the LHA platform. Then, secondly, the ontological phenotype representation can be used to generate search queries that are executed by the LHA Data Portal. The PhenoMan generates the queries in a novel domain specific query language (SDQL), which is specific for data management systems based on CDISC ODM standard, such as the LHA Data Portal. Our approach was successfully applied to represent phenotypes in the Leipzig Health Atlas with the possibility to execute corresponding queries within the LHA Data Portal.

The Process of Modeling Information System Architectures with IHE.

IHE has defined more than 200 integration profiles in order to improve the interoperability of application systems in healthcare. These profiles describe how standards should be used in particular use cases. These profiles are very helpful but their correct use is challenging, if the user is not familiar to the specifications. Therefore, inexperienced modelers of information systems quickly lose track of existing IHE profiles. In addition, the users of these profiles are often not aware of rules that are defined within these profiles and of dependencies that exist between the profiles. There are also modelers that do not notice the differences between the implemented actors, because they do not know the optional capabilities of some actors. The aim of this paper is therefore to describe a concept how modelers of information systems can be supported in the selection and use of IHE profiles and how this concept was prototypically implemented in the "Three-layer Graph-based meta model" modeling tool (3LGM2 Tool). The described modeling process consists of the following steps that can be looped: defining the use case, choosing suitable integration profiles, choosing actors and their options and assigning them to application systems, checking for required actor groupings and modeling transactions. Most of these steps were implemented in the 3LGM2 Tool. Further implementation effort and evaluation of our approach by inexperienced users is needed. But after that our tool should be a valuable tool for modelers planning healthcare information system architectures, in particular those based on IHE.

Problems in FAIRifying Medical Datasets.

Despite their young age, the FAIR principles are recognised as important guidelines for research data management. Their generic design, however, leaves much room for interpretation in domain-specific application. Based on practical experience in the operation of a data repository, this article addresses problems in FAIR provisioning of medical data for research purposes in the use case of the Leipzig Health Atlas project and shows necessary future developments.

Towards Precise Descriptions of Medical Free/Libre and Open Source Software.

The web portal Medfloss.org lists over 360 medical free/libre and open source software (MEDFLOSS) projects. These projects are described with the help of a self-developed nomenclature. Due to inconsistencies, the nomenclature shall be replaced by HITO, the Health IT Ontology. HITO is developed iteratively based on different use cases. This paper aims to describe methods and results of the second HITO use case in which HITO is extended to improve the description, retrieval and comparisons of MEDFLOSS projects on Medfloss.org. We use a mixed-methods approach to add concepts and relationships to describe MEDFLOSS precisely. The resulting HITO version stresses functional descriptions based on features and supported enterprise functions, rather than just describing technical characteristics. However, describing a larger number of MEDFLOSS projects requires the commitment of the community.

Towards a comprehensive and interoperable representation of consent-based data usage permissions in the German medical informatics initiative.

BACKGROUND: The aim of the German Medical Informatics Initiative is to establish a national infrastructure for integrating and sharing health data. To this, Data Integration Centers are set up at university medical centers, which address data harmonization, information security and data protection. To capture patient consent, a common informed consent template has been developed. It consists of different modules addressing permissions for using data and biosamples. On the technical level, a common digital representation of information from signed consent templates is needed. As the partners in the initiative are free to adopt different solutions for managing consent information (e.g. IHE BPPC or HL7 FHIR Consent Resources), we had to develop an interoperability layer. METHODS: First, we compiled an overview of data items required to reflect the information from the MII consent template as well as patient preferences and derived permissions. Next, we created entity-relationship diagrams to formally describe the conceptual data model underlying relevant items. We then compared this data model to conceptual models describing representations of consent information using different interoperability standards. We used the result of this comparison to derive an interoperable representation that can be mapped to common standards. RESULTS: The digital representation needs to capture the following information: (1) version of the consent, (2) consent status for each module, and (3) period of validity of the status. We found that there is no generally accepted solution to represent status information in a manner interoperable with all relevant standards. Hence, we developed a pragmatic solution, comprising codes which describe combinations of modules with a basic set of status labels. We propose to maintain these codes in a public registry called ART-DECOR. We present concrete technical implementations of our approach using HL7 FHIR and IHE BPPC which are also compatible with the open-source consent management software gICS. CONCLUSIONS: The proposed digital representation is (1) generic enough to capture relevant information from a wide range of consent documents and data use regulations and (2) interoperable with common technical standards. We plan to extend our model to include more fine-grained status codes and rules for automated access control.

Design and Concept of the SMITH Phenotyping Pipeline.

Phenotyping means the determination of clinical relevant phenotypes, e.g. by classification or calculation based on EHR data. Within the German Medical Informatics Initiative, the SMITH consortium is working on the implementation of a phenotyping pipeline. to extract, structure and normalize information from the EHR data of the hospital information systems of the participating sites; to automatically apply complex algorithms and models and to enrich the data within the research data warehouses of the distributed data integration centers with the computed results. Here we present the overall picture and essential building blocks and workflows of this concept.

Design of Metadata Services for Clinical Data Interoperability in Germany.

Secondary use of electronic health record (EHR) data requires a detailed description of metadata, especially when data collection and data re-use are organizationally and technically far apart. This paper describes the concept of the SMITH consortium that includes conventions, processes, and tools for describing and managing metadata using common standards for semantic interoperability. It deals in particular with the chain of processing steps of data from existing information systems and provides an overview of the planned use of metadata, medical terminologies, and semantic services in the consortium.

Integrating Heterogeneous Data Sources for Cross-Institutional Data Sharing: Requirements Elicitation and Management in SMITH.

The digitization of health records and cross-institutional data sharing is a necessary precondition to improve clinical research and patient care. The SMITH project unites several university hospitals and medical faculties in order to provide medical informatics solutions for health data integration and cross-institutional communication. In this paper, we focus on requirements elicitation and management for extracting clinical data from heterogeneous subsystems and data integration based on eHealth standards such as HL7 FHIR and IHE profiles.

Towards a Software Tool for Planning IHE-Compliant Information Systems.

As hospital information systems are complex and the requirements for interoperability grow with the increasing networking in healthcare, careful planning becomes more and more necessary. The use of standards as described in IHE profiles, for example, are an important prerequisite for enabling interoperability. Enterprise Architecture Planning (EAP) methods should support this, but none of the currently available EAP methods offers the option of using IHE profiles. The 3LGM2IHE project wants to close this gap and implement the support of IHE profiles in the 3LGM2 tool. This paper describes how requirements for this tool were determined and presents the results.

Smart Medical Information Technology for Healthcare (SMITH).

INTRODUCTION: This article is part of the Focus Theme of Methods of Information in Medicine on the German Medical Informatics Initiative. "Smart Medical Information Technology for Healthcare (SMITH)" is one of four consortia funded by the German Medical Informatics Initiative (MI-I) to create an alliance of universities, university hospitals, research institutions and IT companies. SMITH's goals are to establish Data Integration Centers (DICs) at each SMITH partner hospital and to implement use cases which demonstrate the usefulness of the approach. OBJECTIVES: To give insight into architectural design issues underlying SMITH data integration and to introduce the use cases to be implemented. GOVERNANCE AND POLICIES: SMITH implements a federated approach as well for its governance structure as for its information system architecture. SMITH has designed a generic concept for its data integration centers. They share identical services and functionalities to take best advantage of the interoperability architectures and of the data use and access process planned. The DICs provide access to the local hospitals' Electronic Medical Records (EMR). This is based on data trustee and privacy management services. DIC staff will curate and amend EMR data in the Health Data Storage. METHODOLOGY AND ARCHITECTURAL FRAMEWORK: To share medical and research data, SMITH's information system is based on communication and storage standards. We use the Reference Model of the Open Archival Information System and will consistently implement profiles of Integrating the Health Care Enterprise (IHE) and Health Level Seven (HL7) standards. Standard terminologies will be applied. The SMITH Market Place will be used for devising agreements on data access and distribution. 3LGM2 for enterprise architecture modeling supports a consistent development process.The DIC reference architecture determines the services, applications and the standardsbased communication links needed for efficiently supporting the ingesting, data nourishing, trustee, privacy management and data transfer tasks of the SMITH DICs. The reference architecture is adopted at the local sites. Data sharing services and the market place enable interoperability. USE CASES: The methodological use case "Phenotype Pipeline" (PheP) constructs algorithms for annotations and analyses of patient-related phenotypes according to classification rules or statistical models based on structured data. Unstructured textual data will be subject to natural language processing to permit integration into the phenotyping algorithms. The clinical use case "Algorithmic Surveillance of ICU Patients" (ASIC) focusses on patients in Intensive Care Units (ICU) with the acute respiratory distress syndrome (ARDS). A model-based decision-support system will give advice for mechanical ventilation. The clinical use case HELP develops a "hospital-wide electronic medical record-based computerized decision support system to improve outcomes of patients with blood-stream infections" (HELP). ASIC and HELP use the PheP. The clinical benefit of the use cases ASIC and HELP will be demonstrated in a change of care clinical trial based on a step wedge design. DISCUSSION: SMITH's strength is the modular, reusable IT architecture based on interoperability standards, the integration of the hospitals' information management departments and the public-private partnership. The project aims at sustainability beyond the first 4-year funding period.

Towards Phenotyping of Clinical Trial Eligibility Criteria.

BACKGROUND: Medical plaintext documents contain important facts about patients, but they are rarely available for structured queries. The provision of structured information from natural language texts in addition to the existing structured data can significantly speed up the search for fulfilled inclusion criteria and thus improve the recruitment rate. OBJECTIVES: This work is aimed at supporting clinical trial recruitment with text mining techniques to identify suitable subjects in hospitals. METHOD: Based on the inclusion/exclusion criteria of 5 sample studies and a text corpus consisting of 212 doctor's letters and medical follow-up documentation from a university cancer center, a prototype was developed and technically evaluated using NLP procedures (UIMA) for the extraction of facts from medical free texts. RESULTS: It was found that although the extracted entities are not always correct (precision between 23% and 96%), they provide a decisive indication as to which patient file should be read preferentially. CONCLUSION: The prototype presented here demonstrates the technical feasibility. In order to find available, lucrative phenotypes, an in-depth evaluation is required.

Introducing Technical Aspects of Research Data Management in the Leipzig Health Atlas.

Medical research is an active field in which a wide range of information is collected, collated, combined and analyzed. Essential results are reported in publications, but it is often problematic to have the data (raw and processed), algorithms and tools associated with the publication available. The Leipzig Health Atlas (LHA) project has therefore set itself the goal of providing a repository for this purpose and enabling controlled access to it via a web-based portal. A data sharing concept in accordance to FAIR and OAIS is the basis for the processing and provision of data in the LHA. An IT architecture has been designed for this purpose. The paper presents essential aspects of the data sharing concept, the IT architecture and the methods used.

Technical Environment for Developing the SNIK Ontology of Information Management in Hospitals.

The SNIK project converts textbooks about information management in hospitals to a domain ontology that provides a shared vocabulary for institutions to model and integrate processes, data and infrastructure. To accommodate user groups with different requirements and technical backgrounds, and to support incremental and cooperative development, we create a system architecture to publish, visualize, browse and query the ontology, as well as to evaluate and improve the data quality.

Modeling Requirements for Cohort and Register IT.

BACKGROUND: The project KoRegIT (funded by TMF e.V.) aimed to develop a generic catalog of requirements for research networks like cohort studies and registers (KoReg). The catalog supports such kind of research networks to build up and to manage their organizational and IT infrastructure. OBJECTIVES: To make transparent the complex relationships between requirements, which are described in use cases from a given text catalog. By analyzing and modeling the requirements a better understanding and optimizations of the catalog are intended. There are two subgoals: a) to investigate one cohort study and two registers and to model the current state of their IT infrastructure; b) to analyze the current state models and to find simplifications within the generic catalog. METHODS: Processing the generic catalog was performed by means of text extraction, conceptualization and concept mapping. Then methods of enterprise architecture planning (EAP) are used to model the extracted information. To work on objective a) questionnaires are developed by utilizing the model. They are used for semi-structured interviews, whose results are evaluated via qualitative content analysis. Afterwards the current state was modeled. Objective b) was done by model analysis. RESULTS: A given generic text catalog of requirements was transferred into a model. As result of objective a) current state models of one existing cohort study and two registers are created and analyzed. An optimized model called KoReg-reference-model is the result of objective b). CONCLUSION: It is possible to use methods of EAP to model requirements. This enables a better overview of the partly connected requirements by means of visualization. The model based approach also enables the analysis and comparison of the empirical data from the current state models. Information managers could reduce the effort of planning the IT infrastructure utilizing the KoReg-reference-model. Modeling the current state and the generation of reports from the model, which could be used as requirements specification for bids, is supported, too.